翻訳と辞書
Words near each other
・ Software propagation
・ Software protection dongle
・ Software prototyping
・ Software publisher
・ Software Publishing Corporation
・ Software quality
・ Software quality analyst
・ Software quality assurance
・ Software quality control
・ Software quality management
・ Software Quality Systems AG
・ Software regression
・ Software rejuvenation
・ Software release life cycle
・ Software release train
Software reliability testing
・ Software remastering
・ Software rendering
・ Software repository
・ Software requirements
・ Software requirements specification
・ Software review
・ Software rot
・ Software sampler
・ Software security assurance
・ Software Shelf International
・ Software sizing
・ Software Spectrum
・ Software standard
・ Software Star


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Software reliability testing : ウィキペディア英語版
Software reliability testing
Software reliability testing is a field of software testing that relates to testing a software's ability to function, given environmental conditions, for a particular amount of time. Software reliability testing helps discover many problems in the software design and functionality.
==Overview==
Software reliability is the probability that software will work properly in a specified environment and for a given amount of time. Using the following formula, the probability of failure is calculated by testing a sample of all available input states.
:Probability = Number of failing cases / Total number of cases under consideration
The set of all possible input states is called the input space. To find reliability of software, we need to find output space from given input space and software.
For reliability testing, data is gathered from various stages of development, such as the design and operating stages. The tests are limited due to restrictions such as cost and time restrictions. Statistical samples are obtained from the software products to test for the reliability of the software. Once sufficient data or information is gathered, statistical studies are done. Time constraints are handled by applying fixed dates or deadlines for the tests to be performed. After this phase, design of the software is stopped and the actual implementation phase starts. As there are restrictions on costs and time, the data is gathered carefully so that each data has some purpose and gets its expected precision.
To achieve the satisfactory results from reliability testing one must take care of some reliability characteristics.
For example Mean Time to Failure (MTTF) is measured in terms of three factors:
# operating time,
# number of on off cycles,
# and calendar time.
If the restrictions are on operation time or if the focus is on first point for improvement, then one can apply compressed time accelerations to reduce the testing time. If the focus is on calendar time (i.e. if there are predefined deadlines), then intensified stress testing is used.〔

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Software reliability testing」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.